fix(redirects): add no-slash redirect for /agent-platform/capabilities/computer-use - #485
Conversation
…s/computer-use Vercel matches redirect sources as exact path strings, so the existing trailing-slash rule never fires for the no-slash URL published in a blog post, which 404s instead of reaching the canonical Computer Use page. Co-Authored-By: Warp <agent@warp.dev> Co-Authored-By: Warp Agent <agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@warp-agent-staging[bot] I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
There was a problem hiding this comment.
Overview
This PR adds the missing no-slash Vercel redirect for /agent-platform/capabilities/computer-use, matching the existing trailing-slash redirect to /agents/capabilities/computer-use/ with a permanent 308.
Concerns
- None.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
CodeQL default-setup jobs were cancelled after sitting queued without a runner. Empty commit to retrigger checks. Co-Authored-By: Warp Agent <agent@warp.dev>
Summary
https://docs.warp.dev/agent-platform/capabilities/computer-use(no trailing slash) — the URL published in a blog post — returns 404. Vercel matches redirectsourcevalues as exact path strings, so the existing/agent-platform/capabilities/computer-use/rule (trailing slash) never fires for the no-slash form.This adds the missing no-slash twin in
vercel.json, pointing at the same canonical destination and using the same permanent308status as its neighbors:{ "source": "/agent-platform/capabilities/computer-use", "destination": "/agents/capabilities/computer-use/", "statusCode": 308 }The existing trailing-slash rule is left untouched. Scope is deliberately limited to the reported path; other
/agent-platform/capabilities/*entries share the same gap but are out of scope here.Verification
Live check against this PR's Vercel preview deployment (
docs-git-factory-quality-1520-no-slash-comput-cd831c-warpdotdev.vercel.app):GET /agent-platform/capabilities/computer-use(no slash)308→/agents/capabilities/computer-use/, following it lands200GET /agent-platform/capabilities/computer-use/(existing rule)308→/agents/capabilities/computer-use/— unchangedGET /agents/capabilities/computer-use(canonical)200GET https://docs.warp.dev/agent-platform/capabilities/computer-use(production, unfixed)404— the reported symptomRepo checks
npm run typecheck— pass (0 errors, 0 warnings).npm run build— pass (364 pages built).python3 scripts/check_redirects.py(repo's redirect validator, static mode) — 740 broken destinations both before and after this change, i.e. no regression; the new entry's destination/agents/capabilities/computer-use/resolves and is not among the flagged entries.vercel.jsonparses as valid JSON and the newsourceis not duplicated anywhere in theredirectsarray.Build, link-check, audit) — pass. The three CodeQLAnalyzechecks are red, but that is a repo-wide default-setup failure unrelated to this change: every CodeQL run since ~16:56 UTC is red, including the run onmainand on PRs Restore custom Kapa chat with trigger-based support handoff #466, chore: drafting signal logs #467, docs(skills): improve drafting skills from signal log patterns 2026-08-06 #484, and docs: consolidate the Warp Agent CLI docs into the Agents section #486. GitHub does not allow re-running a default-setup CodeQL run.Regression test — testing-exempt category: config-only. The change is one declarative redirect entry; a unit test could only assert the literal value back rather than detect a logic defect, and the behavior itself is produced by the Vercel platform at request time. The live preview checks above are the deterministic proof.
Closes QUALITY-1520.
Computer-use video recordings
Visiting production and preview docs URLs: Loading the production no-slash docs URL, then the preview deployment's no-slash URL and the page it resolves to, then the preview trailing-slash URL, keeping the address bar visible throughout.
Computer-use screenshots (2)
Production docs.warp.dev no-slash URL showing a "Page not found" page with the address bar visible.
Preview deployment no-slash URL redirected to /agents/capabilities/computer-use/ showing the "Computer Use for agents" documentation page with the address bar visible.
Originating thread: https://warpdev.slack.com/archives/C0BDQDW8V5E/p1786036844862749